change blueprint to not need a synthesized test entrypoint #2071
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ef4
force-pushed
the
no-test-entrypoint
branch
from
0b5f61a to
d86a27a
Compare
add test fixes for no-test-entrypoint branch
This was referenced Aug 30, 2024
patricklx
reviewed
Aug 31, 2024
|
|
||
| {{content-for "body-footer"}} | ||
| {{content-for "test-body-footer"}} |
There was a problem hiding this comment.
Should this be removed? It's still created in
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We no longer need to synthesize a dedicated test entrypoint, vite's built-in features (like eager import.meta.glob) are sufficient.